Summary

• Move the Render Blueprint from the repository root to docs-site/render.yaml.
• Configure the service with rootDir: docs-site, an inline Build Command that generates dist/site before go build, and startCommand: ./app.
• Update docs-site deployment notes for the Render UI settings.

Why

The default Render Go service command can run go build -tags netgo -ldflags '-s -w' -o app from the wrong directory. From the repo root, that builds the root library package into a non-executable app archive, which then fails at start with ./app: Permission denied. From docs-site without the custom build sequence, main.go can fail because //go:embed dist/site requires generated output to exist first.

The Blueprint now lives next to the docs-site service config and uses the same Root Directory shape as the Render UI: Root Directory docs-site, Build Command from docs-site/render.yaml, Start Command ./app.

Verification

• git diff --cached --check
• Created a minimal docs-site/dist/site/index.html and ran go build -tags netgo -ldflags '-s -w' -o app . from docs-site to verify the embed compile path once generated output exists.

Note: I did not run the full docs-site production build locally because the downloaded Tailwind standalone binary was killed by this macOS environment before GOWDK could run the CSS processor.